%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Scenario 8.1 A new customer
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\subsection{Scenario 8.1 A new customer}

This scenario is about Elke, a new customer who wants to register with SAB. The use case touched in this scenario is UC3: Register new customer.

The sequence diagram that covers this scenario is shown in figure \ref{fig:seq_8_1_aNewCustomer} on page \pageref{fig:seq_8_1_aNewCustomer}.

Before the Employee starts working with the \emph{Employee Web App} he needs to log in. Afterwards he will need to log out. This functionality, together with the inner workings of \emph{Employee Web App} are illustrated with a separate diagram for readability. See figure \ref{fig:seq_Employee_Web_app_use_by_Bank_Clerk.png} on page \pageref{fig:seq_Employee_Web_app_use_by_Bank_Clerk.png}.
In the illustration, the \texttt{method(Parameter)} calls are replaced by the corresponding methods and parameters that are provided by the used interfaces. The \texttt{Return} object is the corresponding returned object. \emph{Internal Components} represents all possible components that can be called.

The use cases touched in this scenario are:
\begin{itemize}
 \item UC1: Log in
 \item UC2: Log off
\end{itemize}


\begin{figure}[!ht]
    \centering
        \includegraphics[angle=90, width=0.8\textwidth]{Scenarios/scenario_img/8_1_aNewCustomer.png}
    \caption{Register a new customer}
    \label{fig:seq_8_1_aNewCustomer}
\end{figure}



\begin{figure}[!ht]
    \centering
        \includegraphics[width=1.0\textwidth]{Scenarios/scenario_img/Employee_Web_app_use_by_Bank_Clerk.png}
    \caption{Employee Web App usage by a bank clerk}
    \label{fig:seq_Employee_Web_app_use_by_Bank_Clerk.png}
\end{figure}
